Phase 1: Java 8 to Java 17 Migration - Dependency Compatibility Assessment

Summary

This PR implements Phase 1 of the Java 8 to Java 17 migration for the BankApp Spring Boot application. This phase only updates dependency versions in pom.xml to be compatible with Java 17 - no code changes are included.

⚠️ IMPORTANT: This PR will intentionally break the application's ability to compile and run. Code changes to adapt to the new dependencies will be handled in subsequent phases.

Key Changes:

• Spring Boot: 2.1.4.RELEASE → 3.4.10 (requires Java 17 minimum)
• Java version: 1.8 → 17
• Swagger/OpenAPI: Replaced springfox-swagger2 + springfox-swagger-ui with springdoc-openapi-starter-webmvc-ui 2.8.13
• H2 & Lombok: Versions now managed by Spring Boot 3.4.10 parent (auto-updated to compatible versions)

Review & Testing Checklist for Human

Risk Level: 🟡 YELLOW - Medium risk due to major version jumps and intentionally incomplete changes

• Validate Spring Boot version choice: Confirm 3.4.10 is the right choice vs. 3.5.x or other stable releases
• Review migration strategy: Confirm that dependency-first approach makes sense vs. doing everything at once
• Verify springdoc-openapi replacement: Ensure this is the correct replacement for springfox and version 2.8.13 is appropriate
• Test POM validation: Run mvn validate and mvn dependency:resolve to confirm no dependency resolution issues
• Review migration documentation: Check PHASE1_MIGRATION_REPORT.md accurately describes what needs to be done in subsequent phases

Recommended Test Plan:

1. Pull the branch and run mvn validate - should succeed
2. Run mvn dependency:resolve - should succeed
3. Run mvn compile - should fail (this is expected due to javax→jakarta namespace changes needed)
4. Review the migration plan and ensure subsequent phases are clearly scoped

Notes

• Maven validation and dependency resolution were tested and pass successfully
• Application will not compile until Phase 2+ address code changes (javax→jakarta namespace, Spring Security config, Swagger config updates)
• The detailed migration plan and rationale for all version choices are documented in PHASE1_MIGRATION_REPORT.md

Session Details:

• Link to Devin run: https://app.devin.ai/sessions/255c8878925049cd937a4ee4fa1b6706
• Requested by: @ankehao-dev